Configuration, compilation and getting started with the software:
3.1. Q - Configuration
A - The software has been written to be used with the M8722NF system board. We have not
tested the software with the Microchip Development Board since some hardware
dependencies (namely I/O port availability) are completely different.
The software is controlled by the following files:
sysconfig.h - Start from here!
Most system options are here.
System clock frequency, baud rate, and I/O peripheral availability
can be set by the user.
The file is heavily commented.
global.h - A few important system variables can be set from here.
Namely: GTEMPBUF_SIZE.
For the most part this file does not need to be changed.
compiler.h - Some system defines are here.
For the most part this file does not need to be changed.
machine.h - Some system defines are here.
For the most part this file does not need to be changed.
macrtl.h - If the ports that control the NIC chip ever need to be
changed, check here.
For the most part this file does not need to be changed.
3.2. Q - User modifications
A - We strongly suggest that you use RCS for your checkin/checkout. When the software
installs, it creates the RCS directory and pre-initializes the source files to the latest version.
3.3 Q - Compilation information and analysis.
A - The sequence of events that get executed, for each compilation, are as follows:
1. "make" is invoked with a file name (for a single file compilation) or
"make" by itself compiles and links the software.
2. The ccpicc wrapper script runs and the following steps are performed:
2.1 The compiler environment is prepared via the proper command line arguments.
2.2 The file gets preprocessed by the cdbx utility which expands the "!dxxx"
statements.
2.3 The current lastrun.txt file gets copied to the LASTRUN directory.
The lastrun.txt file holds the output from the link process.
2.4 The source file gets compiled.
2.5 If a link is also required, the software gets linked together.
3. Then, from Windows and using MPLAB, the project .coff file is imported
and then the device is programmed.
4. Next, we test the software and repeat the build process if needed.
